#161522 (comment)

Anyone have an idea how we would do that?

Anyone have an idea how we would do that?

I'm able to get their CI's build process on macos to work if I have a Rustup-based toolchain, it has conveniences to download and install the wasm32-unknown-unknown target as needed.

They also currently target Rust 1.71.1. Do you think it's preferable to:

1. Honor the toolchain used in their build by depending on rustup-init for :build and doing something similar to signal-cli here? Or
2. If it builds with current Rust 1.76.0, then try and get the standard rust formula to work with the build?

It seems like both are doable, but I'm wondering whether there is a strong preference to stick with the same Rust toolchain version as the upstream project? If there is then I would try the first option.

Honor the toolchain used in their build by depending on rustup-init for :build and doing something similar to signal-cli here? Or

That's not an option. It would essentially break https://docs.brew.sh/Acceptable-Formulae#we-dont-like-install-scripts-that-download-unversioned-things and https://docs.brew.sh/Acceptable-Formulae#stuff-that-requires-vendored-versions-of-homebrew-formulae.

If it builds with current Rust 1.76.0, then try and get the standard rust formula to work with the build?

This is the only way really.

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. To keep this pull request open, add a help wanted or in progress label.